Vcenter ResourcePool ResourceAllocationUpdateSpec
The resource_allocation_update_spec schema descrives the updates to be made to the resource allocation settings of a resource pool.
This schema was added in vSphere API 7.0.0.0.
{
"reservation": 0,
"expandable_reservation": false,
"limit": 0,
"shares": {
"level": "string",
"shares": 0
}
}Amount of resource that is guaranteed available to a resource pool. Reserved resources are not wasted if they are not used. If the utilization is less than the reservation, the resources can be utilized by other running virtual machines. Units are MB fo memory, and MHz for CPU.
This property was added in vSphere API 7.0.0.0.
If missing or null or empty, reservation will be set to 0.
In a resource pool with an expandable reservation, the reservation can grow beyond the specified value, if the parent resource pool has unreserved resources. A non-expandable reservation is called a fixed reservation.
This property was added in vSphere API 7.0.0.0.
If missing or null or empty, expandable_reservation will be set to true.
The utilization of a resource pool will not exceed this limit, even if there are available resources. This is typically used to ensure a consistent performance of resource pools independent of available resources. If set to -1, then there is no fixed limit on resource usage (only bounded by available resources and shares). Units are MB for memory, and MHz for CPU.
This property was added in vSphere API 7.0.0.0.
If missing or null or empty, limit will be set to -1.
Shares are used in case of resource contention.
This property was added in vSphere API 7.0.0.0.
If missing or null or empty, shares will be set to 'Vcenter ResourcePool SharesInfo Level.NORMAL'.